Ranking Clusters Based on Facial Image Analysis

ABSTRACT

A user&#39;s collection of images may be analyzed to identify people&#39;s faces within the images, then create clusters of similar faces, where each of the clusters may represent a person. The clusters may be ranked in order of size to determine a relative importance of the associated person to the user. The ranking may be used in many social networking applications to filter and present content that may be of interest to the user. In one use scenario, the clusters may be used to identify images from a second user&#39;s image collection, where the identified images may be pertinent or interesting to the first user. The ranking may also be a function of user interactions with the images, as well as other input not related to the images. The ranking may be incrementally updated when new images are added to the user&#39;s collection.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to and the benefit of U.S.Provisional Patent Application Ser. No. 61/309,029 entitled “RankingBased on Facial Image Analysis” filed 1 Mar. 2010 by Eyal Krupka, et.al., the entire contents of which are hereby expressly incorporated byreference.

BACKGROUND

Image collections reflect important elements by the collection creator.For example, a user's personal image collection may be collected over anextended period of time and may reflect important elements in a person'slife, such as important people. Many people may have image collectionsthat include a wide range of images, from snapshots taken on a mobiletelephone to composed images taken with a digital camera while onvacation, for example.

SUMMARY

A user's collection of images may be analyzed to identify people's faceswithin the images, then create clusters of similar faces, where each ofthe clusters may represent a person. The clusters may be ranked in orderof size to determine a relative importance of the associated person tothe user. The ranking may be used in many social networking applicationsto filter and present content that may be of interest to the user. Inone use scenario, the clusters may be used to identify images from asecond user's image collection, where the identified images may bepertinent or interesting to the first user. The ranking may also be afunction of user interactions with the images, as well as other inputnot related to the images. The ranking may be incrementally updated whennew images are added to the user's collection.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings,

FIG. 1 is a diagram illustration of an embodiment showing an system witha social network and image matching system.

FIG. 2 is a diagram illustration of an example embodiment showingexample images.

FIG. 3 is a flowchart illustration of an embodiment showing a method fordetermining people rankings from images.

FIG. 4 is a flowchart illustration of an embodiment showing a method forfinding matching images based on facial analysis.

FIG. 5 is a flowchart illustration of an embodiment showing a method forpre-processing for facial analysis.

FIG. 6 is a flowchart illustration of an embodiment showing a method forsetting a threshold value with a training set.

FIG. 7 is a flowchart illustration of an embodiment showing a method forevent matching.

FIG. 8 is a flowchart illustration of an embodiment showing a method forusing event matching to find friend's images.

FIG. 9 is a flowchart illustration of an embodiment showing a method forusing event matching to find images for events a user attended.

FIG. 10 is a diagram illustration of an example embodiment showing auser interface with event-matched output.

FIG. 11 is a flowchart illustration of an embodiment showing a methodfor creating clusters.

FIG. 12 is a flowchart illustration of an embodiment showing a methodfor matching images using clusters.

DETAILED DESCRIPTION

Facial image analysis and comparison of a user's image collection may beused to rank a user's preferences or priorities relating to theirfriends or family. A user's image collection may reflect the user'sinterest, importance, or affection for people. The quantity of images ofa particular person may be used as a proxy for the person's importanceto a user.

The facial image analysis may be performed over an image collection toidentify faces within the images and create facial objects, which may bestored as metadata for an image. The facial objects may be representedgrouped together into clusters of faces. The size of the clusters may beused as a measure of the importance of the friend associated with thefacial object.

The ranking determined from the facial image analysis may be used topresent relevant information to the user. For example, newsfeeds orother information that relates to different users may be prioritized andpresented to a user with the more relevant information in a moreprominent position in a user interface.

Throughout this specification and claims, references to the term ‘image’may include static images, such as photographs or digital still images,as well as video images or motion picture images. The concepts discussedfor processing images may be adapted to either still or moving imagesand in some embodiments, both still and moving images may be used.

Throughout this specification, like reference numbers signify the sameelements throughout the description of the figures.

When elements are referred to as being “connected” or “coupled,” theelements can be directly connected or coupled together or one or moreintervening elements may also be present. In contrast, when elements arereferred to as being “directly connected” or “directly coupled,” thereare no intervening elements present.

The subject matter may be embodied as devices, systems, methods, and/orcomputer program products. Accordingly, some or all of the subjectmatter may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, state machines, gate arrays,etc.) Furthermore, the subject matter may take the form of a computerprogram product on a computer-usable or computer-readable storage mediumhaving computer-usable or computer-readable program code embodied in themedium for use by or in connection with an instruction execution system.In the context of this document, a computer-usable or computer-readablemedium may be any medium that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device.

The computer-usable or computer-readable medium may be for example, butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. By way of example, and not limitation, computer-readable mediamay comprise computer storage media and communication media.

Computer storage media includes volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and may be accessed by an instructionexecution system. Note that the computer-usable or computer-readablemedium can be paper or other suitable medium upon which the program isprinted, as the program can be electronically captured via, forinstance, optical scanning of the paper or other suitable medium, thencompiled, interpreted, of otherwise processed in a suitable manner, ifnecessary, and then stored in a computer memory.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” can bedefined as a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in the signal. By wayof example, and not limitation, communication media includes wired mediasuch as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RE, infrared and other wireless media. Combinations ofany of the above-mentioned should also be included within the scope ofcomputer-readable media.

When the subject matter is embodied in the general context ofcomputer-executable instructions, the embodiment may comprise programmodules, executed by one or more systems, computers, or other devices.Generally, program modules include routines, programs, objects,components, data structures, and the like, that perform particular tasksor implement particular abstract data types. Typically, thefunctionality of the program modules may be combined or distributed asdesired in various embodiments.

FIG. 1 is a diagram of an embodiment 100, showing a client and servercomponents for a social network. Embodiment 100 is a simplified exampleof a network environment that may include a client device and a socialnetwork service accessed through a network.

The diagram of FIG. 1 illustrates functional components of a system. Insome cases, the component may be a hardware component, a softwarecomponent, or a combination of hardware and software. Some of thecomponents may be application level software, while other components maybe operating system level components. In some cases, the connection ofone component to another may be a close connection where two or morecomponents are operating on a single hardware platform. In other cases,the connections may be made over network connections spanning longdistances. Each embodiment may use different hardware, software, andinterconnection architectures to achieve the described functions.

Embodiment 100 illustrates an example of a social network in which auser may have collection of images. The social network may be a webapplication in which various users may establish accounts in the socialnetwork and may manage image collections within the social network. Aservice operating within the social network infrastructure may analyzeand compare the image collections.

The social network of embodiment 100 may be any type of social networkin which express or implied relationships may exist between users. Insome social networks, the relationships may be expressed by one userformally establishing a relationship with another user. Some socialnetwork may establish a one-way relationship through such a relationshipdeclaration, while other social networks may establish a relationshipwhen both users approve the relationship.

Some social networks may have informal relationships between users. Forexample, an informal relationship may be established when two usersexchange email messages, or when the users communicate using anothermechanism. For example, a social network may be established for userswho communicate in a chat room, instant messaging service, or othermechanism. In some cases, a person's list of contacts in an email systemor a mobile telephone may be used as an implied relationship for thepurposes of establishing a social network relationship.

In some social networks, a user may determine how images within theirimage collections may be shared. In some cases, a user may select imagesthat may be sharable to friends for which a relationship exists. Inother cases, a user may permit any user with which to share images.

The social network may be a formal social network in which each user maycreate an account to access the social network. In many suchembodiments, the users may access the social network through a webbrowser, and the social network may be a web application. In many suchembodiments, a user may upload images to create an image collectioninside the social network environment.

In less formal versions of a social network, a user may store and managean image collection on a personal computer or in repositories that arepersonally controlled or managed by the user. In such a social network,the user may identify various storage locations from which images may beshared with other people. In some such social network, the socialnetwork relationships may be maintained using infrastructure that may bemerely an address exchange, forum, or other mechanism by which membersmay connect with each other.

The client device 102 may have a set of hardware components 104 andsoftware components 106. The client device 102 may represent any type ofdevice that may communicate with a social network service 136.

The hardware components 104 may represent a typical architecture of acomputing device, such as a desktop or server computer. In someembodiments, the client device 102 may be a personal computer, gameconsole, network appliance, interactive kiosk, or other device. Theclient device 102 may also be a portable device, such as a laptopcomputer, netbook computer, personal digital assistant, mobiletelephone, or other mobile device.

The hardware components 104 may include a processor 108, random accessmemory 110, and nonvolatile storage 112. The hardware components 104 mayalso include one or more network interfaces 114 and user interfacedevices 116. In many cases, the client device 102 may include cameras118 or scanners 120 that may capture images that may become part of auser's image collection.

The software components 106 may include an operating system 112 on whichvarious applications may execute, such as a web browser 124. In manysocial networking applications, a web browser 124 may be used tocommunicate with a social network service 136 to access a social networkapplication. In other embodiments, a specialized client application maycommunicate with a social network service to provide a user interface.In some such embodiments, such a client application may perform manyfunctions that may be described in the social network service 136.

The client device 102 may have a local image library 126 that mayinclude images that are collected from many different sources, such as acamera 118, scanner 120, or other devices that may have image capturecapabilities. The local image library 126 may include images that arestored on other devices, such as a server within a local area network orwithin a cloud storage service, for example.

The client device 102 may have several applications that may allow auser to view and manage the local image library 126. Example of suchapplications may be an image editor 130 and image browser 132. In somecases, a client device may have several such applications.

The local image library 126 may include both still images and videoimages. In some embodiments, still images and video images may be storedin different libraries and may be accessed, edited, and manipulated withdifferent applications.

In some embodiments, the client device 102 may have an imagepre-processor 128. The image pre-processor may analyze the imagecontents as well as various metadata associated with the image prior toassociating the image with a social network. The pre-processing mayperform facial image analysis, background analysis, color histograms, orother analyses on images available to the client. In other embodiments,some or all of the functions performed by the image pre-processor 128may be performed by the social network service 136. When an imagepre-processor 128 is located on the client device 102, a server devicemay be offloaded from performing such operations.

The client device 102 may connect to the social network service 136through a network 134. In some embodiments, the network 134 may be awide area network, such as the Internet. In some embodiments, thenetwork 134 may include a local area network which may be connected to awide area network through a gateway or other device.

In some embodiments, the client device 102 may connect to the network134 through a hard wired connection, such as an Ethernet connection, forexample. In other embodiments, the client device 102 may connect to thenetwork 134 through a wireless connection, such as a cellular telephoneconnection or other wireless connection.

Various users of the social network may connect using various clientdevices 138.

The social network service 136 may operate on hardware platform 140. Thehardware platform 140 may be a single server device that has a hardwareplatform similar to the hardware components 104 of the client device102. In some embodiments, the hardware platform 140 may be a virtualizedor cloud based hardware platform that operates on two or more hardwaredevices. In some embodiments, the hardware platform may be a largedatacenter in which many hundreds or thousands of computer hardwareplatforms may be used.

The social network service 136 may operate within an operating system142 in some embodiments. In embodiments that have cloud based executionenvironments, the notion of a separate operating system 142 may notexist.

The social network 144 may include multiple user accounts 146. Each useraccount 146 may include metadata 148 relating to the account, as well asrelationships 150 that may be established between two or more users.

The user account metadata 148 may include information about the user,such as the user's name, home address, location, as well as the user'slikes and dislikes, education, and other relevant information. Somesocial networks may have emphasis on work related information, which mayinclude items like work history, professional associations, or otherjob-related information. Other social networks may emphasize friends andfamily relationships where personal items may be emphasized. In somesocial networks, very large amounts of personal metadata 148 may beincluded, while other social networks may have very little amount ofpersonal metadata 148.

The relationships 150 may associate one user account to another. In someembodiments, the relationships may be one-way relationships, where afirst user may share information with a second user but the second usermay not reciprocate and may share no information or a limited amount ofinformation with the first user. In other embodiments, the relationshipsmay be two-way relationships where each user agrees to share informationwith each other.

In still other embodiments, a user may allow some or all of theirinformation to be shared to anyone, including people who are not membersof the social network. Some such embodiments may allow a user toidentify a subset of information that may be shared to anyone, as wellas subsets that may be shared with other members of the social network.Some embodiments may allow a user to define subsets that are shared withdifferent groups of social network members.

Each user account 146 may include one or more image collections 152. Theimage collections 152 may include images 154. Each image 154 may includemetadata 156, which may be general metadata such as timestamp, locationinformation, image size, title, and various tags. The tags may includeidentifiers for different social network members to which the image mayrelate.

In some embodiments, the image metadata 156 may contain metadata derivedfrom the image contents. For example, a facial analysis may be performedto identify any faces within the image and to create a facialrepresentation or facial vector. The facial representation may be usedto compare with other images, for example. Other image contents that maybe used to derive metadata may include texture analysis of backgroundareas or a person's clothing, color histograms of the entire image orportions of the image, or other analyses.

The image metadata 156 may be used to create clusters 158. The clusters158 may be groupings of images or elements from images. For example,facial representations may be analyzed to identify clusters that containsimilar facial representations. Similarly, clusters may be created bygrouping image analysis results from background areas of the images.

In some embodiments, clusters 158 may be created by grouping imagesbased on metadata. For example, several images that are taken during acertain time period may be grouped together as a cluster, or images thatare tagged with the same tag parameter may form a cluster. Examples ofuses clusters may be found in embodiments 1100 and 1200 presented laterin this specification.

In some embodiments, the social network service 136 may include an imagepre-processor 160 that may analyze images to derive image metadata. Theimage pre-processor 160 may be used for instances where a client device102 may not have an image pre-processor 128 or when image pre-processingis not performed prior to analysis. An example of the pre-processingsteps may be illustrated in embodiment 500 presented later in thisspecification.

A comparison engine 162 may compare two or more images using imageanalysis techniques or metadata analysis to determine the clusters 158.An example of the operations of a comparison engine 162 may be found inportions of embodiment 400 presented later in this specification.

A ranking engine 164 may compare the various clusters 158 to extractinformation, such as the ranking or importance of the images orinformation attached to the images. An example of the operations of aranking engine 164 may be found in embodiment 300 presented later inthis specification.

An analysis engine 166 may analyze and compare image collections toidentify matches between the image collections. The analysis engine 166may use metadata analysis and image content analysis to identifymatches.

In many embodiments, a social network service 136 may operate with a webservice 168 that may communicate with browsers or other applicationsoperable on a client device. The web service 168 may receive requests inHyper Text Transmission Protocol (HTTP) and respond with web pages orother HTTP compliant responses. In some embodiments, the web service 168may have an application programming interface (API) through which anapplication on a client device may interact with the social networkservice.

FIG. 2 is a diagram of an example embodiment 200, showing two imagesthat may be analyzed by image analysis. Embodiment 200 illustrates twoimages 202 and 204 that show a birthday party and a sailing excursion,respectively. The images may represent example images that may be foundin a user's image collection.

Image 202 may represent a birthday party with two people. From the image202, two faces 206 and 208 may be identified. Several different facialrecognition mechanisms or algorithms may be used to identify the faces206 and 208.

Once identified, the faces 206 and 208 may be processed to createrepresentations of the faces. The representations may be facial vectorsor other representations that may allow numerical comparisons ofdifferent faces to each other.

In some embodiments, additional image analyses may be performed. Forexample, the clothing areas 210 and 212 may be identified by determininga geometrical relationship from the faces 206 and 208, respectively, andcapturing a portion of an image that may relate to the clothing beingworn by the respective people.

Image analysis of clothing may be used to compare two images todetermine if those images were taken at the same event. Such aconclusion may be drawn when two images contain similar faces and theimages additionally contain similar clothing textures or colorhistograms. Such an analysis may assume that the images represent thesame event because the people in the images may be wearing the sameclothes.

Additionally, a background area 214 may be analyzed for textureanalysis, color histogram, or other analyses. Such results may becompared to other images to determine similarities and matches betweenthe images.

In the image 204, the faces 216 and 218 may be identified and captured.Because the size of the faces 216 and 218 may be relatively small, theclothing areas for the people of image 204 may not be performed, but abackground area 220 may be identified and analyzed.

FIG. 3 is a flowchart illustration of an embodiment 300 showing a methodfor determining people rankings from an image collection. Embodiment 300is an example of a method that may be performed by a comparison engineand ranking engine, such as comparison engine 162 and ranking engine 164of embodiment 100.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

Embodiment 300 may be an example of a method by which the number ofoccurrences of a person's face in a user's image collection may be usedas an approximation of the user's interest in the person or theimportance of the person to the user.

The faces within the images may be analyzed, compared, and groupedtogether into clusters. Based on the size of the clusters, the personsassociated with the clusters may be ranked.

An image collection may be received in block 302. The image collectionmay be pre-processed to identify faces and facial representations. Anexample of such a pre-processing method may be illustrated in embodiment500 presented later in this specification.

Each image may be processed in block 304. For each image in block 304,if no faces exist in block 306, the process may return to block 304 toprocess the next image. If one or more faces appear in the image inblock 306, each face may be separately processed in block 308. For eachface in block 308, the face object and the associated image referencemay be added to a list in block 310. The image reference may be apointer or other indicator for the image from which the face is taken.

After processing all of the images in block 304, the resulting list maybe sorted in block 312.

In block 314, the list may be analyzed to identify clusters based on athreshold value in block 314. The clusters may define a group of facialrepresentations that relate to a single person.

One mechanism to determine a cluster may be to consider a facialrepresentation as a vector. The similarity between any two vectors maybe considered a distance in the vector space. When multiple facialrepresentations reflect many different images of the same person, thefacial representation vectors may create clusters of vectors.

In many embodiments, a threshold may be used as part of a mechanism todetermine whether or not a given facial representation is ‘close’ toanother facial representation to be a match. The threshold may bedetermined in several different manners, and one such manner may beillustrated in embodiment 600.

Each cluster may be analyzed in block 316. For each cluster in block316, if any members of the cluster do not have tags or other associatedmetadata in block 318, the process may return to block 316 to processanother cluster.

If one or more of the members of the cluster in block 318 contains tagsor other metadata, those tags may be applied to other cluster members inblock 320. In some cases, the user may be presented with a userinterface device in block 322 where the user may approve or disapprovethe tags. If the user approves the tags in block 324, the tags may beapplied to all members of the cluster in block 326. If the user does notapprove the tags in block 324, the tags may not be applied to themembers in block 328.

In many social network applications, users may tag images withidentifiers for specific people, for example. The process of blocks 316through 328 may represent a method by which such tags may be applied toother images automatically. In some embodiments, the tags applied to themembers of the cluster may be tags that relate to the person the clustermay represent. A simple example may be a tag that defines the person'sname.

The clusters may be analyzed in block 330 to rank the clusters accordingto size. The ranking may reflect the relative importance of the peopleto the user. The cluster rankings may be used in block 332 to prioritizepeople in various applications.

For example, a newsfeed may include messages, status updates, or otherinformation that relate to people in a user's social network. Thoseitems relating to important people may be highlighted or presented in amanner that captures the user's attention. Other items concerning peoplewho do not appear often in the user's image collection may be presentedin a secondary or non-emphasized manner.

FIG. 4 is a flowchart illustration of an embodiment 400 showing a methodfor finding matching images based on facial analysis. Embodiment 400 isan example of a method that may be performed by a comparison engine,such as analysis engine 166 of embodiment 100.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

Embodiment 400 illustrates an example of a method by which images from asecond image collection may be compared to a first image collection toidentify images in the second image collection that contain the samepeople as the first image collection.

A second image collection may be received in block 402. The second imagecollection may be pre-processed in block 404. One example of a methodfor pre-processing may be illustrated in embodiment 500 presented laterin this specification.

Each image in the second image collection may be processed in block 406.For each image in block 406, if no faces are found in block 408, theprocess may return to block 406 to process the next image.

If faces are found in block 408, each face object may be processed inblock 410. For each face object in block 410, a comparison may be madeto the clusters of the first image collection in block 412 to find theclosest match. If the match does not meet the threshold in block 414,the process may return to block 410 to process the next face object. Ifthe match is within the threshold in block 414, the image is associatedto the cluster in block 416.

After processing all of the images in block 406, the result may be alist of images from the second image collection that match clusters inthe first image collection. The list may be ranked in block 418according to the ranking that may be determined from the process ofembodiment 300, and presented to the user.

FIG. 5 is a flowchart illustration of an embodiment 500 showing a methodfor pre-processing images for facial analysis. Embodiment 500 is anexample of a method that may be performed by an image pre-processor,such as the image pre-processor 128 of client 102 or image pre-processor160 of a social network service 136 of embodiment 100.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

The pre-processing of embodiment 500 may identify faces and create facevectors or some other numerical representation of a facial image for allimages in an image collection.

An image file may be received in block 502 and may be scanned in block504 to identify all faces.

If faces are found in block 506, each face may be separately processedin block 508. For each face in block 508, the image may be cropped tothe face in block 510 and a face object may be created from the croppedimage in block 512. A face vector may be created in block 514 which maybe a numerical representation of the face image. The face vector andface object may be stored as metadata for the image in block 516.

After all the faces are processed in block 508, if another image isavailable in block 518, the process may loop back to block 502,otherwise the process may stop in block 520.

FIG. 6 is a flowchart illustration of an embodiment 600 showing a methodfor setting a threshold value using a training set of images. Embodiment600 is an example of a method that may gather example images fromfriends of a user and use those example images to set a threshold thatmay minimize false positive comparisons.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

Embodiment 600 may determine a threshold setting that may minimize falsepositive comparisons when comparing image collections. In many socialnetwork applications, a relatively high confidence threshold may beuseful to minimize the likelihood of incorrectly identifying a match.When selecting photographs or video images from a second user's imagecollection to match a first user's image collection, an incorrect matchmay give a user a low confidence in the matching process. However, amissed match, where the match exists but the threshold does not permitthe match to be detected, may not be as detrimental to the user'sconfidence.

The process of embodiment 600 gathers representative images from auser's friend's image collection to serve as a training set forcomparisons. Facial comparisons may differ based on race, skin color,and other physical characteristics of those people associated with theuser. The images selected may be from the user's friend's friends, andmay reflect the probable physical characteristics of the people in theuser's image collection.

The process of embodiment 600 may attempt to remove any people from thetraining set who may be likely to be in the user's image collection.This may be performed by examining any tags associated with the friend'simages to ensure that the tags do not match the user's friends.

The user's friends may be identified in block 602. The user's friendsmay be determined from relationships within the social network, as wellas any other source. In some cases, a user may belong to several socialnetworks, each with a different set of relationships. In such cases, asmany of those relationships may be considered as possible.

Each of the user's friends may be processed in block 604. For eachfriend in block 604, each image in the friend's image collection isprocessed in block 606. For each image in block 606, the tags associatedwith the image may be identified in block 608. If the tags areassociated with friends of the user in block 610, the image is notconsidered in block 610. By excluding the friends of the user in block610, the training set may not include images that are likely to bematches for the user, but may include images of people having similarcharacteristics as people likely to be in the user's image collection.

If the tags indicate that the image may not be related to the user inblock 610, the image may be selected for the training set in block 612.In many cases, the images selected for the training set may be a subsetof all of the images in the friend's image collection. For example, aprocess may select one out of every 100 or 1000 candidate images as partof a training set. In some embodiments, a random selection may be madefor the training set.

After selecting images to be in a training set in blocks 604 through612, a facial pre-processing may be performed on the training set inblock 614. The pre-processing may be similar to that of embodiment 500.

The matching threshold may be set to a default value in block 616.

Each image of the user's image collection may be processed in block 618to set the threshold so that none of the images in the user's imagecollection match the training set. For each image in block 618, if theimage does not contain faces in block 620, the process returns to block618.

When the image contains faces in block 620, each face may be processedin block 622. For each face in block 622, the face object may becompared to face objects in the training set find the most similar faceobject in block 624. If the similarity is less than the threshold inblock 626, the process may return to block 622. If the similarity isgreater than the threshold in block 626, the threshold is adjusted inblock 628 so that the threshold is lower than the similarity in block628.

After processing all of the images in the user's image collection inblock 618, the current threshold value may be stored in block 630 andused for subsequent comparisons.

FIG. 7 is a flowchart illustration of an embodiment 700 showing a methodfor event matching. Embodiment 700 is a simplified example of a methodthat may be performed by an analysis engine, such as the analysis engine166 of embodiment 100.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

Embodiment 700 is an example of a method that may be used to detect anevent from metadata. The metadata may be metadata that may be derivedfrom an image, such as from facial analysis or other image analysis. Themetadata may also be metadata that is not derived from the image, suchas a title, timestamp, or location information.

Embodiment 700 may infer an event from the intersection of the imagecollections of two users. Such an intersection may occur when both usersattend the same event and both take images of the event. For example,two users may attend a birthday party or family gathering and takepictures of a family gathered for a meal. In another example, two usersmay attend a conference, sporting event, or other public event and maytake images of the gathering. In some cases, the users may know abouteach other's attendance of the event and in other cases, the users maybe unaware that the other person has attended.

In block 702, an image collection may be received from a first user. Inblock 704, an image collection may be received from a second user. Insome embodiments, the information received may be just the metadatarelated to the images in the collection and not the actual imagesthemselves.

The metadata from each image collection may be compared in block 706 tofind matches. The matches may be based on image analysis, such asfinding matching faces in images from two different collections. Thematches may be based on metadata analysis, such as finding images thathave timestamps, tags, location information, or other metadata that arematches.

In many cases, the matches may be determined with some level oftolerance or variance. The matches identified in block 706 may have alarge amount of variance or tolerance, as each match may be furtherevaluated in later steps. The matching in block 706 may be a coarse orpreliminary matching that may be further refined to identify a matchwith greater certainty.

The results of block 706 may be a pair of images from each collection.In some cases, the results may be a group of images from each collectionthat share similar metadata.

Each set of matched images may be compared in block 708. For each set ofmatched images in block 708, the metadata may be compared in block 710to determine if an event can be inferred.

An event may be inferred based on several factors. Some factors may beweighted highly, while other factors may be of a secondary nature. Thedetermination of whether a match indicates an event or not may bedetermined using various heuristics or formulas, and such heuristics orformulas may depend on the embodiment. For example, some embodiments mayhave extensive metadata available, while other embodiments may havefewer metadata parameters. Some embodiments may have sophisticated imageanalysis while other embodiments may have less sophisticated or even noimage analysis.

A highly weighted factor may be in cases where the second useridentifies the first user in one of the second user's images. Suchmetadata expressly identifies a link between the two image collectionsand indicates that both users were likely to be in the same place at thesame time.

In some embodiments, users may tag images in their collections withpersons from their social network. In such embodiments, a user maymanually select an image and create a tag that identifies a friend inthe image. Some such embodiments may allow the user to point to the faceand attach the tag to a location on the image. Such tags may beconsidered reliable indicators and given higher weight than othermetadata.

Other highly weighted factors may be very close proximity in space andtime. Very close timestamps and physical location information mayindicate that two users were at the same time and place. In someembodiments, an image may include a point from which an image was takenas well as a direction that a camera was facing when the image wastaken. When such metadata are available, the overlap of the area coveredby two images may be evidence of an event.

Some images may be tagged with various descriptors that are manuallyadded by a user. For example, an image may be tagged with “Anna'sBirthday Party” or “Tech Conference”. When images from both imagecollections are similarly tagged, the tags may be good indicators of anevent.

The matches may be analyzed using image analysis to identify commonevents. For example, a facial image match between images in bothcollections may be a good indicator of an event attended by and capturedby both users. A facial image match may be further confirmed by similarbackground image areas and by clothing analysis of people associatedwith the matched faces.

When identifying a common event, different combinations of factors maybe used in different situations and different embodiments. For example,an event may be determined by image analysis alone in some cases, evenwhen the metadata do not correlate. For example, one user may purchase acamera device and may never correctly set the time and date in thecamera, or may have the time set to a different time zone than the otheruser. In such a case, the timestamp metadata may be incorrect, but theimage analysis may identify a common event.

In another example, the metadata may identify a common event even thoughthe image analysis may not identify any common faces, background, orother similarities.

Different embodiments may have different thresholds for identifying anevent. In a typical social network use of embodiment 700, the analysismay be performed to automatically apply tags to images based on theevents. In such an embodiment, a higher degree of certainty may bedesired so that incorrect tags are not introduced into the imagecollection as noise. In another use, the matching may be used toidentify possible events that a user may manually examine to determineif an event actually did occur. In such a use, the threshold todetermine an event may have a much lower degree of certainty than in theother use case.

If an event is not determined in block 712, the process may return toblock 708 to process another match.

If an event is identified in block 712, all images associated with theevent may be identified in block 714. A metadata tag may be defined forthe event in block 716, and the tag may be applied to the images inblock 718.

The images associated with the event may be determined by identifyingimages that are related to or share common metadata or other featureswith the matched images. For example, two images may be matched, onefrom either image collection. Once those images are matched, any relatedimages to the matched images within their respective collections may beidentified in block 714.

The metadata tag in block 716 may be generated by scanning the relatedimages to determine if an event tag is associated with any of therelated images. For example, one of the images that was gathered inblock 714 may be tagged with an event tag, such as “Anna's Birthday”.That tag may then be applied to all of the related images in block 718.

In some embodiments, the event tag of block 716 may be an automaticallygenerated event tag that may identify how the match was determined. Forexample, a match that was determined by common metadata having time andlocation information may have a tag that includes “Jerusalem, 22 Feb.2010”. Each embodiment may have different mechanisms for determining atag.

In some embodiments, the tag applied in block 718 may not be visible toa user. Such a tag may be used by a social network to link differentimage collections together to provide enhanced search or browsingcapabilities and may not expose the tag to the user for viewing ormodification.

FIG. 8 is a flowchart illustration of an embodiment 800 showing a methodfor event matching between a user's image collection and those of theuser's friends. Embodiment 800 is a simplified example of a use scenariofor the event matching method described in embodiment 700.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

Embodiment 800 compares a user's image collection to those of the user'sfriends. The comparison may identify events that were shared by the twousers and may identify images in the friend's image collection that thefirst user may like to add to his or her image collection.

Embodiment 800 may be a powerful tool for linking two image collectionstogether in a social network. In some uses, the two users may know thatthey have attended the same event and may wish to share their imageswith each other. In other uses, the users may not remember attending thesame event or may not realize that both were there. The method ofembodiment 800 may enhance the users' interaction by identifying theintersections in their lives and allowing them to share the eventthrough their images.

In block 802, a user's image collection may be received. The user'sfriends may be identified in block 804 and each friend may be processedin block 806. For each friend in block 806, event matching may beperformed in block 808 between the user and the user's friend toidentify common events. The event matching may be performed in a similarmanner as described in embodiment 700.

Each new event that was found in block 808 may be analyzed in block 810.For each new event in block 810, images may be selected from thefriend's image collection in block 812 that match the event. Anymetadata from the selected images from the friend's image collection maybe identified in block 814 and applied to the user's images that arerelated to the event in block 816.

The operations of block 814 and 816 may propagate tags and othermetadata from the friend's image collection to the user's imagecollection. In some embodiments, a user may be given an option toapprove or disapprove the tagging. The tags and other metadata mayenrich the user's image collection by applying useful tags automaticallyor semi-automatically.

The friend's images may be presented to the user in block 818 and may begrouped by event. An example of a user interface may be illustrated inembodiment 1000 presented later in this specification.

After processing each event in block 810, the user may browse thefriend's images and select one or more of the friend's images in block820. The selected images may be added to the user's image collection inblock 822.

FIG. 9 is a flowchart illustration of an embodiment 900 showing a methodfor event matching between pairs of a user's friends. Embodiment 900 isa simplified example of a use scenario for the event matching methoddescribed in embodiment 700.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

Embodiment 900 compares two of a user's friend's image collections toidentify events that can be inferred from two of the user's friends.Images from the inferred events may be presented to the user and theuser may add those images to the user's image collection.

Embodiment 900 may be useful in a social network scenario where a usermay or may not be present at an event and may wish to view images of theevent and may add some of those images to the user's image collection.For example, grandparents who are unable to attend a grandchild's partymay wish to see images of the party. The party may be inferred byanalyzing image collections from two or more people that attended theparty. By inferring the event from analysis of the image collections,all of the relevant images to the event may be gathered and presented tothe grandparents for them to enjoy.

Embodiment 900 operates in a similar manner as embodiment 800, howeverthe image collections used for the event matching may be pairs ofcollections from the user's friends as opposed to comparing a user'scollections to those of his or her friends.

A user's friends may be identified in block 902 and placed in a list.The friends may be identified through a social network. Each friend maybe processed in block 904. For each friend in block 904, each remainingfriend on the list of friends may be analyzed in block 906. Theremaining friends are those friends for which an image collection hasnot been processed. For each remaining friend in block 906, an eventmatching process may be performed between the two friend's imagecollections in block 908 to identify common events. The process ofblocks 904 and 906 may be arranged so that each pair of friends may beprocessed to identify common events.

Each common event may be processed in block 910. For each common eventin block 910, some embodiments may include verification in block 912 todetermine if the user could have been present.

The verification of block 912 may be used to prevent showing an event towhich the user was not invited. For example, two of a user's friends mayget together for a night on the town and may not invite the user. Toprevent the user from being insulted, some embodiments may includeverification such as block 912 to prevent the user from finding out thatthe event occurred. In other embodiments, such as with the example withthe grandparents above, the verification of block 912 may not beincluded or may be overridden.

In some social networks, a user may be able to select whether or not toshare the events with other users, and may be able to select which usersmay view their common events and which users may not.

In block 914, images from the friend's image collection may be selectedfrom the common event and presented to the user in block 916 grouped bythe event. After processing all the common events in block 910, the usermay browse and select images in block 918 and may add selected images tothe user's collection in block 920.

FIG. 10 is a diagram illustration of an example embodiment 1000 showinga user interface with results from an event matching analysis.Embodiment 1000 is a simplified example of a user interface that may beused to present the results of an event matching analysis to a user,such as the event matching analysis of embodiments 800 or 900.

A user interface 1002 may display the results of an event matchingprocess. In the user interface 1002, results from three events areillustrated. Event 1004 may have a tag “Birthday Party”, event 1006 mayhave a tag “Holiday at Beach” and event 1008 may have a tag “SkiingVacation”. The various tags may be identified from tags defined from theimage collections of the friends. In some cases, the tags may bedetermined from the user's images that match the detected events.

Each event may be presented with a source for the images. For example,event 1004 may have an image source 1010 of “From Mom's and Joe'sCollection”. Event 1006 may have an image source 1012 of “From Joe'sCollection”, and event 1008 may have an image source 1014 of “FromLora's Collection”. The image sources may be created using the user'slabels for the user's friends.

The user interface 1002 may also include various metadata relating tothe event. For example, event 1004 may be presented with metadata 1016that indicates which of the user's friends were determined to be at theevent. Similarly, event 1006 and 1008 may have metadata 1018 and 1020,respectively.

Each event may have a selection of images presented. Event 1004 is shownwith images 1022, 1024, and 1026. Event 1006 is shown with images 1028and 1030, and event 1008 is shown with image 1032. Next to each imagemay be a button or other mechanism by which a user may select one ormore images to add to the user's image collection.

The user interface of embodiment 1000 is merely one example of some ofthe components that may be presented to a user as a result of imagematching analysis, such as event matching. The user interface may be amechanism by which a user may browse the results of a match analysis andperform operations on the results.

FIG. 11 is a flowchart illustration of an embodiment 1100 showing amethod for creating clusters that maybe used for matching images.Embodiment 1100 is a simplified example of one method by which clustersmay be created by analyzing a single image collection and groupingimages. The clusters may be used in image comparison analyses andmetadata comparison analyses.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

Embodiment 1100 may illustrate a simplified method for creating clustersof images. A cluster may be a group of images that may share commonfeatures, and may be useful in grouping faces as well as grouping imagesas a whole.

A cluster may be created by identifying a vector that represents theimage and by grouping the vectors together. A cluster may have acentroid and radius, and numerical comparisons may be made between animage and the cluster to determine a ‘distance’ between the image andcluster to determine a match.

An image collection may be received in block 1102 and each image in theimage collection may be analyzed in block 1104. In embodiments wherefacial recognition is used, the images may be face objects that maycontain only the facial features of people cropped from larger images.In such embodiments, the analysis may create a vector that representsthe face object. In other embodiments, the entire image may be analyzedto create an image vector.

The image may be analyzed in block 1106 to create an image vector. Theimage vector may contain numerical representations of various elementsof the image, including facial image analysis, clothing analysis,background image analysis, and texture analysis.

In some embodiments, the analysis of block 1106 may create several imagevectors. For example, an image having two faces may be represented withtwo image vectors representing the faces, two image vectors representingthe clothing of the two people, and one or more vectors representingbackground images or various textures in the image.

After each image is analyzed in block 1104, the images may be groupedtogether in block 1108. The grouping may be using both metadata groupingand image analysis grouping. One mechanism for grouping may be to groupimages together on independent or orthogonal grouping axes for eachmetadata category or type of image analysis. For example, one groupingaxis may be established for facial image analysis. On such an axis, allfacial image representations or vectors may be grouped. Separately, eachimage may be grouped according to different metadata, such as timestampor location.

Within each axis, clusters may be identified in block 1110. Thedefinition of a cluster may be controlled using a threshold that maylimit clusters to tight groupings of images. The clusters may be used torepresent actual matches of images with a high degree of certainty sothat other operations, such as image comparisons and ranking may have ahigh degree of certainty.

Each axis on which the images are grouped may have a different thresholdfor identifying a cluster. For example, facial image matching may have arelatively tight threshold so that only matches with very high degree ofsimilarity may be considered a cluster. Conversely, images that arematched by background image analysis may have a less restrictivethreshold so that a wider range of images may be grouped.

Each cluster may have a centroid and radius calculated in block 1112.The centroid and radius may be used to determine matches when otherimages are compared to the image collection. The clusters as well as thecentroid and radius may be stored in block 1114.

FIG. 12 is a flowchart illustration of an embodiment 1200 showing amethod for matching images using centroid and radius analysis ofclusters. Embodiment 1200 may illustrate one method by which theanalyzed images of embodiment 1100 may be used to identify matchesbetween a user's image collection and a friend's image collection, thento select the most appropriate or best match to display to the user.

Other embodiments may use different sequencing, additional or fewersteps, and different nomenclature or terminology to accomplish similarfunctions. In some embodiments, various operations or set of operationsmay be performed in parallel with other operations, either in asynchronous or asynchronous manner. The steps selected here were chosento illustrate some principles of operations in a simplified form.

A user's image collection may be received in block 1202, and a friend'simage collection may be received in block 1204. The user's friend'simage collection may be pre-processed in block 1205. An example of apre-processing method may be embodiment 500. The pre-processing ofembodiment 500 may apply to facial image analysis, and may be extendedto background image analysis, texture analysis, color histogramanalysis, clothing analysis, and other image analysis pre-processing.

The pre-processing of block 1205 may correspond to any analysisperformed prior to clustering of the user's image collection.

Each image in the friend's image collection may be analyzed in block1206. For each image in block 1206, each cluster associated with theuser's image collection may be analyzed in block 1208.

As described in embodiment 1100, each image collection may containmultiple clusters in multiple orthogonal axes. Each cluster mayrepresent an important aspect or element of the user's image collection,and those aspects may be used to compare with the images from thefriend's image collection.

For each cluster in block 1208, a distance from the analyzed image tothe nearest cluster may be determined in block 1210. If the distance iswithin a centroid matching threshold in block 1212, the image may beassociated with the cluster in block 1218.

If the distance is not within the centroid matching threshold in block1212, a distance to the nearest neighbor may be determined in block1214. If the distance to the nearest neighbor is not within the neighborthreshold in block 1216, no match is determined.

The nearest neighbor may be an image that is within the cluster. Thenearest neighbor evaluation may identify images that fall outside of thecluster but very near one of the images that has been grouped with thecluster. In a typical embodiment, the neighbor threshold may be smallwhen compared to the centroid threshold.

After analyzing all of the images in the friend's image collection inblock 1206, the friend's images may be selected for presentation to theuser.

The user's clusters may be ranked by size in block 1220. The ranking maybe used as a proxy for importance to the user. Each cluster may beevaluated in block 1222. For each cluster in block 1222, the matchedimages may be compared to the clusters to find the closest image to aneighbor in block 1224 and to a cluster centroid in block 1226. The bestmatch may be determined in block 1228 and added to a user interfacedisplay in block 1230.

The process of blocks 1220 through 1230 may identify those matches thatmay be the most relevant to the user as well as the most likely to begood matches. The relevance may be determined by the ranking of theclusters derived from the user's image collection. The best matches maybe those images that are nearest to the centroid of a cluster or verynear to another image, which may be represented by the nearest neighbor.

Image matching may be prone to noise and many image matching algorithmsmay result in false positive results, where an image is incorrectlymatched. In a social networking application that has image matching,user satisfaction with the matching mechanism may be higher when theuser is presented with quality matches.

The process of blocks 1220 through 1230 may select the best match fromthe available matches to present to the user. Such a process may selecta representative match for each cluster and present each match to theuser, enabling the user to view a wide variety of matches.

After selecting the images, the images may be presented to the userorganized by cluster in block 1232. The user may browse and selectimages in block 1234 and may add the images to the user collection inblock 1236.

In some embodiments, the user may be able to drill down into the matchesfor a particular cluster to view additional matches. In such a case, theprocess of blocks 1220 through 1230 may be used to organized and selectthe most appropriate images from the subset of images matching theparticular cluster.

The foregoing description of the subject matter has been presented forpurposes of illustration and description. It is not intended to beexhaustive or to limit the subject matter to the precise form disclosed,and other modifications and variations may be possible in light of theabove teachings. The embodiment was chosen and described in order tobest explain the principles of the invention and its practicalapplication to thereby enable others skilled in the art to best utilizethe invention in various embodiments and various modifications as aresuited to the particular use contemplated. It is intended that theappended claims be construed to include other alternative embodimentsexcept insofar as limited by the prior art.

1-20. (canceled)
 21. A system comprising: at least one hardwareprocessor; and at least one memory or non-volatile storage media storingcomputer-readable instructions which, when executed by the at least onehardware processor, cause the at least one hardware processor to: accessan image collection of a user, the image collection comprising aplurality of images; based at least on metadata associated with theplurality of images of the image collection, identify selected personidentities that are present in the plurality of images; access aplurality of data items other than the images of the image collection;select, from the plurality of data items, one or more selected dataitems that relate to the selected person identities that are present inthe plurality of images in the image collection of the user; and providethe selected data items to the user.
 22. The system of claim 21, whereinthe plurality of data items comprises another image collection ofanother user, and the selected data items comprise other images from theanother image collection.
 23. The system of claim 21, wherein theplurality of data items comprises messages or status updates directed tothe user, and the selected data items comprise a subset of the messagesor status updates.
 24. The system of claim 21, wherein thecomputer-readable instructions, when executed by the at least onehardware processor, cause the at least one hardware processor to:identify a plurality of person identities that are present in theplurality of images; and select the selected person identities from theplurality of person identities based at least on occurrences ofindividual person identities in the image collection.
 25. The system ofclaim 24, wherein the metadata identifies face objects associated withthe individual person identities, each face object comprising arespective occurrence of a respective person identity.
 26. The system ofclaim 25, wherein the computer-readable instructions, when executed bythe at least one hardware processor, cause the at least one hardwareprocessor to: select the selected person identities by ranking theindividual person identities relative to one another based at least onindividual numbers of occurrences of the face objects of the individualperson identities.
 27. The system of claim 21, wherein thecomputer-readable instructions, when executed by the at least onehardware processor, cause the at least one hardware processor to:receive the plurality of images over a network from a client deviceassociated with the user; and provide the selected data items to theuser by sending the selected data items over the network to the clientdevice associated with the user.
 28. A method comprising: accessing afirst image collection comprising a plurality of first images and asecond image collection comprising a plurality of second images;performing image processing on the first images of the first imagecollection and the second images of the second image collection; basedat least on the image processing, inferring that a particular event isrepresented in a particular first image of the first image collectionand a particular second image of the second image collection; andperforming event-specific processing on at least one of the particularfirst image or the particular second image.
 29. The method of claim 28,wherein the event-specific processing comprises tagging the particularsecond image with a particular metadata value identifying the particularevent.
 30. The method of claim 29, further comprising: obtaining theparticular metadata value identifying the particular event from metadataassociated with the particular first image.
 31. The method of claim 28,further comprising: inferring that a plurality of events are representedin the first image collection and the second image collection; andgrouping individual second images of the second image collection intoindividual event-specific groups for individual events of the plurality.32. The method of claim 31, wherein the first image collection isassociated with a first user and the second image collection isassociated with a second user.
 33. The method of claim 32, furthercomprising: presenting individual second images of the second imagecollection to the first user such that the individual second images aregrouped according to the individual event-specific groups.
 34. Themethod of claim 32, performed by a social networking application thatprovides a first account to the first user and a second account to thesecond user, wherein the first user and the second user have apredefined relationship maintained by the social networking application.35. The method of claim 34, further comprising: identifying a third userthat has a predefined relationship with the first user and the seconduser and that is not in present in any image associated with theparticular event; and preventing the third user from viewing theparticular event.
 36. The method of claim 28, wherein the imageprocessing comprises analyzing at least one of backgrounds or clothingpresent in individual first images of the first image collection andindividual second images of the second image collection to infer thatthe particular event is represented therein.
 37. A client devicecomprising: a processor; and computer storage media storingcomputer-readable instructions which, when executed by the processor,cause the processor to: send, over a network to a remote service, aplurality of images having person identities present in the images,wherein the remote service stores the images in an image collectionassociated with a user of the client device; access the remote serviceto obtain content other than the images of the image collection;receive, over the network from the remote service, one or more selecteddata items other than the plurality of images of the image collection,wherein the one or more selected data items are selected by the remoteservice and relate to selected person identities that are present in theplurality of images of the image collection; and display the selecteddata items received from the remote service.
 38. The client device ofclaim 37, wherein the remote service comprises a social networkingservice with which the user of the client device has a correspondingaccount.
 39. The client device of claim 37, wherein the one or moreselected data items comprise other images from another image collectionof another user of the remote service.
 40. The client device of claim37, wherein the one or more selected data items comprise messages orstatus updates directed to the user of the client device via the remoteservice.